NeXT TypedStream Data | 1996-11-08 | 21.0 KB | 504 lines
typedstream
IBObjectData
Object
CustomObject
Application
MenuTemplate
*@*@ccc
The NoSD Submitter
Matrix
Control
Responder
@:@iiii
MenuCell
ButtonCell
ActionCell
Helvetica
Info Panel...
Preferences...
Categories
Help...
ff@@#::s
submenuAction:
NXImage
NXmenuArrow
NoSD Sheet
Open...
Save As...
Save To...
Save All
Revert to Saved
Close
Send by Mail
Paste
Select All
Windows
Arrange in Front
Miniaturize Window
Close Window
ClipView
ScrollView
Scroller
_doScroller:
@@@ffs
NXCursor
NXibeam
ciifffcfffs
[9883c]{\rtf0\ansi{\fonttbl\f0\fswiss Helvetica;}
\margl40
\margr40
{\colortbl;\red0\green0\blue0;}
\pard\tx3620\f0\b\i0\ulnone\fs48\fc1\cf1 General Information\
\b0\fs24 \
Version 0.9, 03 May 1995\
After launching The_NoSD_Submitter, you will be presented with an Inspector panel style window containing several inspectors with groups of fields and pop up menus. \
The inspectors you will need to invoke to complete the information contained in a description are:\
-Submitter Information, to type in your name and e-mail adress, \
-Author-Information, where you should supply information on the developer or company who has developed the product, \
-Product-Information, to characterize the software object, and, finally, \
-Versions-Information, to supply necessary information on the ports, the version, and the creation date.\
The descriptions, once generated, can be stored and revoked for further editing, using the normal commands. Also, a description can be sent to the NoSD group via e-mail. The e-mail adress may be edited before mailing in order to provide a correct adress scheme for any kind of internet access.\
\b\fs48 \
Submitter-Information
\b0\fs24 \
Enter YOUR name here. e-mail will be sufficient.\
\b\fs48 \
Author Information
\b0\fs24 \
Into these fields should be typed information about the author or the developing company. You may exclude certain kinds of information, e.g. your phone number, if you don't want a millon people on the phone.\
\b\fs36 Name\
\b0\fs24 \
Enter description/contact information about the authors/creators of the object in this field. For commercial objects, the company name should appear here.\
\b\fs36 \
Work-Phone
\b0\fs24 \
Enter phone number of author or company.\
\b\fs36 \
Work-Fax
\b0\fs24 \
Fax number of author or company.\
\b\fs36 \
Work-Postal
\b0\fs24 \
Postal adress of author or company as normally formated. Should also contain the country. \
\b\fs36 \
E-mail\
\b0\fs24 \
e-mail adress of author or company.\
\b\fs48 Product Information
\b0\fs24 \
The fields in this group should characterize the object as completely as possible, including hardware and software requirements; whether the object is sold in a bundle, whether it is a plug in module to some other software etc. \
\b\fs36 Title
\b0\fs24 \
Title of the product. This field should normally contain the name of the
*.app
*.pkg
config
etc. file of the object. If a bundle of several products is to be described in the template, the name for the bundle as commercialized should be given.\
\b\fs36 Category
\b0\fs24 \
The nomination of the category to which the object belongs, is based on a five letter code, wherein the first two letters mark the broad range, the other three further specifiy the category. Up to five categories may be named, separated by commas and spaces. For a complete list of valid categories, invoke he command "Info" "Categories. In a later version of this program, we plan to have a nicer interface to choose the categories (e.g. a browser). In fact, this is the reason for the version number 0.9. \
Since it is very difficult to cover the hole range of existing or possible software, we would like to get further input and improvements from the community. Should an object belong to several categories, those should be given in descending order of appliance. If, for a certain object, none of the categories should seem to fit, a proposal for a new category should be filed to me@thyls.muc.de. \
\b\fs36 \
Requirements
\b0\fs24 \
Any requirements for the use of the object. Enter a free text description of any\
hardware/software requirements necessary to use the object. Not longer than 250 characters.
\fc0\cf0 Also, if the Kanji version of NEXTSTEP is required, this should be noted here.
\fc1\cf1 \
\b\fs36 Description
\b0\fs24 \
Description of the object. Any marketing hype should be avoided. The lenght of this field is (almost) not limited. Hence, you can supply a considerable amount of information, if necessary. Nevertheless, be as clear and concise as possible. \
Now, the tough stuff: If your software object is presently missing a feature which everybody would normally expect in such kind of software (like a word processor which offers multi-columns, but no document sections, the latter feature rendering the former almost unusable) , please also mention this to allow potential users/customers to decide if they would absolutely need this feature.\
If the software has a command line interface, not a NEXTSTEP-GUI, please also indicate this.\
If this record is to describe a bundle of objects, a reference to the products comprising the bundle should be made, e.g. by quoting "BUNDLE FOR". \
If the object is part of another object, the description should start with
PART OF:
followed by the name of the bundle as given in the record (file/NoSD entry) which describes this bundle.\
\b\fs36 Short-Description\
\b0\fs24 \
Short characterization with not more than 30 characters.\
\b\fs36 Copyright Type
\b0\fs24 \
This pop up menu is to indicate the copyright type of the object.\
Valid denominators are:\
\b commercial
\b0 : Commercial product\
\b publicdomain
\b0 : Freely distributable, no charge\
\b shareware
\b0 : free for testing, has to be lizensed.\
\b freeware
\b0 : freely available, but is copyrighted by the developper\
\b\fs36 Copyright statement\
\b0\fs24 \
Enter a copyright statement. Any additional information on the copying policy may be\
included. Also, pricing can be included, if necessary, in several currencies. Furthermore, it should be indicated whether support for the software will be given by the developper.\
\b\fs36 Keywords
\b0\fs24 \
Enter appropriate keywords for this object into this field. Several keywords should be separated by kommas, each keyword may consist of several words.\
\b\fs36 \
\b0\fs24 \
\b\fs48 Versions-Information
\b0\fs24 \
\b\fs36 Version
\b0\fs24 \
Enter a version designator for the object.\
\b\fs36 Release/Creation-Date\
\b0\fs24 \
The creation date for the object. Can be of the type 12 Apr 1994, or Jan 1994, or 1994, depending on how much information on the precise date is available.\
\b\fs36 Publication-Status
\b0\fs24 \
Indicate in this pop up menu the current publication status of the object\
The following denominators are valid:\
\b available
\b0 : product is available\
\b beta
\b0 : product is currently tested\
\b planned
\b0 : planed release\
\b obsolete
\b0 : product is still available, but will not run with current versions of NEXTSTEP\
\b defunct
\b0 : product is no longer available. However, one may still be able to get a copy from somewhere.\
\b\fs36 Architectures:\
\b0\i NEXTSTEP
\i0\fs24 \
Check here which NEXTStep versions which are available. \
The text aside the buttons stands for:\
\b motorola
\b0 : NeXT computers\
\b intel
\b0 : IBM compatible computers\
\b HP-PA
\b0 : HP-Workstations or compatibles\
\b SPARC
\b0 : Sparc compliant computers\
\b POWERPC
\b0 : PreP compliant systems \
\i\fs36 OpenStep
\i0\fs24 \
Check here which OpenStep versions are available. The versions should be sufficiently self explanatory. \
\i\fs36 Other
\b\i0 \
\b0\fs24 \
This field is for NEXTSTEP/OpenStep specific Software not running under NS/OS environment (like Netinfo). The versions should be sufficiently self explanatory.\
To facilitate the machine readability of certain data elements, the following syntax applies.\
\b\fs36 E-mail
\b0\fs24 \
All electronic mail (Email) addresses must be as defined in RFC 822, Section 6. Names and comments may be included in the Email address.\
For example:\
"John Doe" <jd@ftp.bar.org>\
or\
jd@ftp.bar.org\
are valid Email addresses.\
\b\fs36 Hostnames
\b0\fs24 \
All hostnames are to be given as Fully Qualified Domain Names as\
defined in RFC 1034, Section 3.\
For example "foo.bar.com"\
All host IP addresses are given in "dotted-quad" (or\
"dotted-decimal") notation. \
For example, "127.0.0.1"\
\b\fs36 Numeric Values
\b0\fs24 \
All numeric values are in decimal unless otherwise stated.\
\b\fs36 Dates
\b0\fs24 \
Dates must be given as defined in RFC 822, Section 5.1 and\
modified in RFC 1123, Section 5.2.14 [7]:\
date-time = [ day "," ] date time ; dd mm yy\
; hh:mm:ss zzz\
day = "Mon" / "Tue" / "Wed" / "Thu"\
/ "Fri" / "Sat" / "Sun"\
date = date = 1*2DIGIT month 2*4DIGIT ; day month year\
; e.g. 20 Jun 82\
month = "Jan" / "Feb" / "Mar" / "Apr"\
/ "May" / "Jun" / "Jul" / "Aug"\
/ "Sep" / "Oct" / "Nov" / "Dec"\
\
For example the string "Sat, 18 Jun 93" is a valid\
date.\
\b\fs36 Text
\b0\fs24 \
All text shall be in NEXTSTEP ASCII, allowing the use of special signs like french accents or german umlauts.\
\
"whitespace" is defined as one or more blank (octal 40) and/or tab (octal 11) ASCII characters.\
\b\fs36 Phone Numbers
\b0\fs24 \
All telephone numbers are to be given as a minimum in full with country and routing codes without separators. The number should be given assuming someone calling internationally. The number given in the local convention may optionally be specified.\
(.txt)